Conversation
beckermr
left a comment
beckermr
left a comment
There was a problem hiding this comment.
The virtual packages are written to disk as a separate channel here: https://github.com/chrisburr/conda-forge-feedstock-check-solvable/blob/fake-archspc/conda_forge_feedstock_check_solvable/virtual_packages.py#L114
We need to add the archspec version / names we support as globals in utils.py and then write them in the same way.
Also we'll need to add tests.
|
I thought I had tried that and it didn't work I'll try again |
|
What do you think about doing the opposite and setting them all properly instead of making a fake channel? |
|
The fake channel is there so that we can use |
|
Given the mamba support will likely be removed how about I port it over and make the fake channel mamba specific? |
|
That'd be fine as long as we have a test that ensure the virtual packages end up the same for each solver. |
|
I pushed changes to at least get the mamba tests to run even if they fail. |
|
Having thought about it more I think the |
chrisburr
changed the title
2 participants
When dependent packages require archspec the bot fails to solve despite the situation being okay. For example: https://conda-forge.org/status/migration/?name=root_base6328
This fixes this by always including the
x86_64_v3virtual package when solving for x86_64. We could think of including other virtual packages but I'm not sure if it's worth it.